fix HTTP/2 docs #3262
Closed
fix HTTP/2 docs #3262
+7
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| *and* the server need to support HTTP/2. If you connect to a server that only | ||
| supports HTTP/1.1 the client will use a standard HTTP/1.1 connection instead. | ||
|
|
||
| To force HTTP/2 to be enabled, disable HTTP/1.1. Otherwise, the client will try to use HTTP/1.1 |
There was a problem hiding this comment.
This isn't correct. Here's the deal...
- Default.
http1=True, http2=False- HTTP/1.1 will be used. - HTTP/2 support enabled.
http1=True, http2=True- Either HTTP/1.1 or HTTP/2 will be used. The protocol negotiation (ALPN) occurs during the SSL setup. - Force HTTP/2.
http1=False, http2=True- HTTP/2 will be used, without negotiation. Not a typically useful configuration, tho allows HTTP/2 over plain HTTP.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note on forcing HTTP/2 to be enabled by disabling HTTP/1.1 for the client
issue: #3261